Skip to content

Allow fork-PR checkout in pull_request_target workflows#1446

Open
JMJBILLINGS wants to merge 3 commits into
Domain-Connect:masterfrom
JMJBILLINGS:fix-pr-target-checkout
Open

Allow fork-PR checkout in pull_request_target workflows#1446
JMJBILLINGS wants to merge 3 commits into
Domain-Connect:masterfrom
JMJBILLINGS:fix-pr-target-checkout

Conversation

@JMJBILLINGS

Copy link
Copy Markdown

Fixes #1445.

All five pull_request_target workflows currently fail at the actions/checkout step for every fork PR — the Actions runner now refuses fork-PR checkout in pull_request_target workflows unless the checkout step sets allow-unsafe-pr-checkout: true (see any recent fork PR's run annotations, e.g. #1444).

This adds that one line to the checkout step in each of the five workflows. Risk note per https://gh.io/securely-using-pull_request_target: these workflows run base-repo tooling (dc-template-linter, check-jsonschema, .github/scripts) against changed root-level JSON files and do not execute contributed code, so the opt-in appears safe here — but please review.

@github-actions

Copy link
Copy Markdown

JSON Filename Check Passed

@github-actions github-actions Bot added the Checklist of common problems not complete See PR template and mark *all* checkboxes, even if not applicable. Explain any discrepancies. label Jul 24, 2026
@github-actions

Copy link
Copy Markdown

JSON Schema Validation Passed

@github-actions github-actions Bot added PR description incomplete The PR description template was not filled in at all, altered or filled in improperly. Test links missing No test links from Online Editor provided automerge-possible Label indicating, that restrictive linter checks all pass. For now it's PoC. labels Jul 24, 2026
@github-actions

Copy link
Copy Markdown

Linter OK

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Linter passed all checks — approving for auto-merge.

@pawel-kow pawel-kow removed the automerge-possible Label indicating, that restrictive linter checks all pass. For now it's PoC. label Jul 24, 2026
@github-actions

Copy link
Copy Markdown

PR Description Check Failed

The PR description is missing required elements. Please update it according to the PR template.

Details

Labels to add: Checklist of common problems not complete, PR description incomplete, Test links missing
Labels to remove: Forged editor links

PR description check FAILED:
  FAIL  'Type of change' section not found
  FAIL  'How Has This Been Tested?' section not found
  FAIL  'Checklist of common problems' section not found
  FAIL  'Online Editor test results' section not found

@github-actions github-actions Bot added the automerge-possible Label indicating, that restrictive linter checks all pass. For now it's PoC. label Jul 24, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Linter passed all checks — approving for auto-merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge-possible Label indicating, that restrictive linter checks all pass. For now it's PoC. Checklist of common problems not complete See PR template and mark *all* checkboxes, even if not applicable. Explain any discrepancies. PR description incomplete The PR description template was not filled in at all, altered or filled in improperly. Test links missing No test links from Online Editor provided

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI broken for all fork PRs — actions/checkout refuses pull_request_target checkout

2 participants